fix: surface mapStateToProps errors in connect - #2311

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Quick follow-up in case this is easier to review now than the other connect PR:

This change is intentionally narrow. It only re-surfaces mapStateToProps subscription errors during render so existing error boundaries can catch them, without changing the successful update path.

If you'd prefer this handled in a different layer of connect, or want the regression coverage trimmed to a smaller repro, I'm happy to adjust.

#2306 already logs these errors in development, and this approach rethrows the saved error even after a later store update or new props would let mapStateToProps succeed. That breaks the existing "throws once, then recovers" test. We're also trying to keep connect behavior changes to a minimum right now. Given that, I'm going to go ahead and close this. Thanks!